Since 9.5.2.1 - locks not cleared properly by "remove lock"

Whenever a user client session crashes and they have a module open in edit mode, removing the lock does not work correctly in 9.5.2.1 - it requires a restart of the server daemons. Before this version, the locks were always removed properly without the need for a daemon restart. When this happens during the day it is a real pain to try and get 100s of users off the system just to remove 1 lock - we have to wait until the next day after the backup cycle has restarted the daemons.

Anyone else experiencing this new 'feature'?

Re: Since 9.5.2.1 - locks not cleared properly by "remove lock"
knobutan - Wed Jul 16 22:02:32 EDT 2014

Hi,

So, you remove the lock using the DBS Admin tool right?

After you unlock, what do you see when you try open the module?? Any error message?

Re: Since 9.5.2.1 - locks not cleared properly by "remove lock"
BillTidy - Thu Jul 17 14:31:43 EDT 2014

First attempt is "Tools" -> "Manage locks" and this always worked in the past (prior to 9.5.2). Now this never works - we see the lock as deleted in the Manage Locks function but we get "Lock request timed out" error on trying to open the module in Edit. So now we always have to go via the server and either restart the daemons or use the DBSAdmin tool. Either way this is a PITA change as our servers are managed by 3rd party support who have no idea about DOORS support (only Linux actions like stop/start daemons).

I was more interested to see if anyone else experiences this also and if it is was a planned change or it is an introduced bug.

Re: Since 9.5.2.1 - locks not cleared properly by "remove lock"
knobutan - Tue Jul 22 03:08:18 EDT 2014

Unfortunately I have never seen or heard of that issue.

So problem here is that you cannot unlock using Tools > Manage locks right?

Will check if there is any defect regards to Manage locks functionality

Re: Since 9.5.2.1 - locks not cleared properly by "remove lock"
Tony_Goodman - Tue Jul 22 05:00:37 EDT 2014

In the past, whenever DOORS crashed potentially leaving locks behind, I have always started a new client and then immediately closed it. This (used to) ensure that all locks were cleared.

Not sure if this is the same issue, but is probably good practice after a crash.

Tony

Re: Since 9.5.2.1 - locks not cleared properly by "remove lock"
BillTidy - Tue Jul 22 13:40:30 EDT 2014

Tony,

This is exactly what we used to do prior to version 9.5.2.1 - in 9.5.2.1 this no longer seems to work.